Method for Determining Network Quality of Service Flow, Network Element, and System

ABSTRACT

A method for determining a network quality of service (QoS) flow, a network element, and a system include receiving, by a session management function network element, a policy and charging control (PCC) rule from a policy control function network element, where the PCC rule includes QoS parameters, the QoS parameters include standardized QoS parameter indication information and a non-standardized QoS parameter, and the non-standardized QoS parameter includes at least one attribute comprised in a standardized QoS parameter corresponding to the standardized QoS parameter indication information and a corresponding value of the at least one attribute, and determining, by the session management function network element based on the standardized QoS parameter indication information and the non-standardized QoS parameter, a QoS flow corresponding to the PCC rule.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No.16/926,203, filed on Jul. 10, 2020, which is a continuation ofInternational Application No. PCT/CN2019/071581 filed on Jan. 14, 2019.The International Application claims priority to Chinese PatentApplication No. 201810031151.1, filed on Jan. 12, 2018. All of theafore-mentioned patent applications are hereby incorporated by referencein their entireties.

TECHNICAL FIELD

This application relates to the communications field, and in particular,to a method for determining a network quality of service (QoS) flow, anetwork element, and a system.

BACKGROUND

In a mobile communications technology, QoS can be guaranteed in agranularity of a QoS flow. Each QoS flow is bound to a correspondingpolicy and charging control (PCC) rule, QoS of a data servicetransmitted using the QoS flow is determined based on QoS parameters inthe PCC rule to which the QoS flow is bound, and a session managementfunction network element binds the PCC rule to the QoS flow. Therefore,how the session management function network element binds the QoS flowto the PCC rule exerts great impact on network QoS of the data service.

SUMMARY

This application provides a method for determining a network QoS flow, anetwork element, and a system such that an accuracy rate of determininga QoS flow corresponding to a PCC rule can be increased, therebyimproving network QoS of a data service.

According to a first aspect, a method for determining a network QoS flowis provided, and the method includes receiving, by a session managementfunction network element, a PCC rule from a policy control functionnetwork element, where the PCC rule includes QoS parameters, and the QoSparameters include standardized QoS parameter indication information anda non-standardized QoS parameter, and the non-standardized QoS parameterincludes at least one attribute comprised in a standardized QoSparameter corresponding to the standardized QoS parameter indicationinformation and a corresponding value of the at least one attribute, anddetermining, by the session management function network element based onthe standardized QoS parameter indication information and thenon-standardized QoS parameter, a QoS flow corresponding to the PCCrule.

Therefore, the session management function network element determines,using both the standardized QoS parameter indication information and thenon-standardized QoS parameter, the QoS flow corresponding to the PCCrule, thereby increasing an accuracy rate of determining the QoS flowcorresponding to the PCC rule, and accordingly guaranteeing network QoSof a data service transmitted using the QoS flow.

With reference to the first aspect, in some implementations of the firstaspect, the standardized QoS parameter indication information is a5^(th) generation (5G) QoS identifier (5QI) parameter value, and thenon-standardized QoS parameter includes at least one of the followingparameters and a corresponding value; a data packet delay budget (PDB),a data packet error rate (PER), an averaging window (AW), a prioritylevel (PL), and a maximum data burst volume (MDBV).

In an existing method for determining a QoS flow corresponding to a PCCrule, the QoS flow corresponding to the PCC rule is usually determinedbased on the standardized QoS parameter indication information withoutconsidering the non-standardized QoS parameter. As a result, PCC ruleshaving different non-standardized QoS parameter requirements are boundto a same QoS flow, and a same QoS guarantee may be used for servicesthat require different QoS guarantees. Consequently, user experience maybe degraded, and QoS cannot be guaranteed. For example, in the otherapproaches, a session management function network element binds, to asame QoS flow, a plurality of PCC rules including a same 5QI value butdifferent non-standardized QoS parameters (for example, PLs). When thesession management function network element receives a PCC rule {5QI: 1;PL: 10}, and determines that a QoS flow {5QI: 1; PL: 30} whose 5QI valueis the same as that of the PCC rule exists in a current protocol dataunit (PDU) session, the session management function network elementbinds the received PCC rule to the QoS flow. In this case, consequently,QoS of a service data flow corresponding to the received PCC rule cannotbe guaranteed (a system provides a service guarantee for the serviceflow according to {5QI: 1; PL: 30}). In this application, when the QoSflow corresponding to the PCC rule is determined, the non-standardizedQoS parameter is considered, for example, at least one of the followingparameters: the PDB, the PER, the AW, the PL, and the MDBV, to ensurethat PCC rules including same standardized QoS parameter indicationinformation but different non-standardized QoS parameters are bound todifferent QoS flows, thereby increasing an accuracy rate of determiningthe QoS flow corresponding to the PCC rule, and improving userexperience.

With reference to the first aspect, in some implementations of the firstaspect, determining a QoS flow corresponding to the PCC rule includes,when there is a first QoS flow that matches both the standardized QoSparameter indication information and the non-standardized QoS parameter,determining, by the session management function network element, thefirst QoS flow as the QoS flow corresponding to the PCC rule, or whenthere is no QoS flow that matches both the standardized QoS parameterindication information and the non-standardized QoS parameter,determining, by the session management function network element, asecond QoS flow as the QoS flow corresponding to the PCC rule, where QoSparameters corresponding to the second QoS flow are determined accordingto the PCC rule.

With reference to the first aspect, in some implementations of the firstaspect, the PCC rule further includes a first parameter, and the firstparameter is any parameter that can represent QoS and that is other thanthe standardized QoS parameter indication information and thenon-standardized QoS parameter. The first parameter may be, for example,an allocation and retention priority (ARP) or a QoS notification control(QNC).

Determining a QoS flow corresponding to the PCC rule includes, whenthere is a first QoS flow that matches all of the standardized QoSparameter indication information, the non-standardized QoS parameter,and the first parameter, determining, by the session management functionnetwork element, the first QoS flow as the QoS flow corresponding to thePCC rule, or when there is no QoS flow that matches all of thestandardized QoS parameter indication information, the non-standardizedQoS parameter, and the first parameter, determining, by the sessionmanagement function network element, a second QoS flow as the QoS flowcorresponding to the PCC rule, where QoS parameters corresponding to thesecond QoS flow are determined according to the PCC rule.

In this case, when the PCC rule further includes the first parameter,the QoS flow corresponding to the PCC rule is determined using thestandardized QoS parameter indication information, the non-standardizedQoS parameter, and the first parameter such that an accuracy rate ofdetermining the QoS flow corresponding to the PCC rule can be furtherincreased.

With reference to the first aspect, in some implementations of the firstaspect, the PCC rule further includes flow matching information, andwhen the session management function network element determines thesecond QoS flow as the QoS flow corresponding to the PCC rule, themethod further includes sending, by the session management functionnetwork element, a flow identifier of the second QoS flow and the QoSparameters to an access network, sending, by the session managementfunction network element, the flow identifier of the second QoS flow andthe flow matching information to a user plane function (UPF) networkelement, and sending, by the session management function networkelement, the flow identifier of the second QoS flow and the flowmatching information to user equipment.

With reference to the first aspect, in some implementations of the firstaspect, the PCC rule further includes flow matching information, andwhen the session management function network element determines thefirst QoS flow as the QoS flow corresponding to the PCC rule, the methodfurther includes sending, by the session management function networkelement, a flow identifier of the first QoS flow and a second parameterto an access network, where the second parameter is indicationinformation for the access network updating a value of an attributecorresponding to a QoS parameter corresponding to the flow identifier ofthe first QoS flow, and sending, by the session management functionnetwork element, the flow identifier of the first QoS flow and the flowmatching information to a UPF network element, and sending, by thesession management function network element, the flow identifier of thefirst QoS flow and the flow matching information to user equipment.

According to a second aspect, a method for determining a network QoSflow is provided, and the method includes determining, by a policycontrol function network element, QoS parameters, where the QoSparameters include standardized QoS parameter indication information anda non-standardized QoS parameter, and the non-standardized QoS parameterincludes at least one attribute comprised in a standardized QoSparameter corresponding to the standardized QoS parameter indicationinformation and a corresponding value of the at least one attribute, andsending, by the policy control function network element, a PCC rule to asession management function network element, where the PCC rule includesthe QoS parameters.

Therefore, the policy control function network element sends the PCCrule to the session management function network element. Because the PCCrule includes the standardized QoS parameter indication information andthe non-standardized QoS parameter, the session management functionnetwork element determines, based on both the standardized QoS parameterindication information and the non-standardized QoS parameter, the QoSflow corresponding to the PCC rule, thereby increasing an accuracy rateof determining the QoS flow corresponding to the PCC rule, andaccordingly improving network QoS of a data service.

With reference to the second aspect, in some implementations of thesecond aspect, the standardized QoS parameter indication information isa 5QI parameter value, and the non-standardized QoS parameter includesat least one of the following parameters and a corresponding value: adata PDB, a data PER, an AW, a PL, and an MDBV.

With reference to the second aspect, in some implementations of thesecond aspect, determining, by a policy control function networkelement, QoS parameters includes receiving, by the policy controlfunction network element, the non-standardized QoS parameter from anapplication function network element, or receiving, by the policycontrol function network element, first indication information from anapplication function network element, and determining, by the policycontrol function network element, the non-standardized QoS parameteraccording to the first indication information and a first pre-configuredpolicy, or receiving, by the policy control function network element,second indication information from the session management functionnetwork element, and determining, by the policy control function networkelement, the non-standardized QoS parameter according to the secondindication information and a second pre-configured policy.

In this case, the policy control function network element determines thenon-standardized QoS parameter such that the policy control functionnetwork element can dynamically determine the QoS parameters in realtime to adjust the PCC rule in a timely manner, and then determine a QoSflow corresponding to an adjusted PCC rule, thereby increasing anaccuracy rate of determining the QoS flow corresponding to the PCC rule,and accordingly improving network QoS of a data service.

According to a third aspect, a session management function networkelement is provided, including a receiving module configured to receivea PCC rule from a policy control function network element, where the PCCrule includes QoS parameters, the QoS parameters include standardizedQoS parameter indication information and a non-standardized QoSparameter, and the non-standardized QoS parameter includes at least oneattribute comprised in a standardized QoS parameter corresponding to thestandardized QoS parameter indication information and a correspondingvalue of the at least one attribute, and a determining module configuredto determine, based on the standardized QoS parameter indicationinformation and the non-standardized QoS parameter, a QoS flowcorresponding to the PCC rule.

With reference to the third aspect, in some implementations of the thirdaspect, the standardized QoS parameter indication information is a 5QIparameter value, and the non-standardized QoS parameter includes atleast one of the following parameters and a corresponding value: a dataPDB, a data PER, an AW, a PL, and an MDBV

With reference to the third aspect, in some implementations of the thirdaspect, the determining module is further configured to, when there is afirst QoS flow that matches both the standardized QoS parameterindication information and the non-standardized QoS parameter,determine, by the session management function network element, the firstQoS flow as the QoS flow corresponding to the PCC rule, or when there isno QoS flow that matches both the standardized QoS parameter indicationinformation and the non-standardized QoS parameter, determine, by thesession management function network element, a second QoS flow as theQoS flow corresponding to the PCC rule, where QoS parameterscorresponding to the second QoS flow are determined according to the PCCrule.

With reference to the third aspect, in some implementations of the thirdaspect, the PCC rule further includes a first parameter, and the firstparameter is any parameter that can represent QoS and that is other thanthe standardized QoS parameter indication information and thenon-standardized QoS parameter, and the determining module is furtherconfigured to, when there is a first QoS flow that matches all of thestandardized QoS parameter indication information, the non-standardizedQoS parameter, and the first parameter, determine, by the sessionmanagement function network element, the first QoS flow as the QoS flowcorresponding to the PCC rule, or when there is no QoS flow that matchesall of the standardized QoS parameter indication information, thenon-standardized QoS parameter, and the first parameter, determine, bythe session management function network element, a second QoS flow asthe QoS flow corresponding to the PCC rule, where QoS parameterscorresponding to the second QoS flow are determined according to the PCCrule.

With reference to the third aspect, in some implementations of the thirdaspect, the PCC rule further includes flow matching information, andwhen the session management function network element determines thesecond QoS flow as the QoS flow corresponding to the PCC rule, thesession management function network element further includes a sendingmodule, and the sending module is configured to send a flow identifierof the second QoS flow and the QoS parameters to an access network, sendthe flow identifier of the second QoS flow and the flow matchinginformation to a UPF network element, and send the flow identifier ofthe second QoS flow and the flow matching information to user equipment.

With reference to the third aspect, in some implementations of the thirdaspect, the PCC rule further includes flow matching information, andwhen the session management function network element determines thefirst QoS flow as the QoS flow corresponding to the PCC rule, thesession management function network element further includes a sendingmodule, and the sending module is configured to send a flow identifierof the first QoS flow and a second parameter to an access network, wherethe second parameter is indication information for the access networkupdating a value of an attribute corresponding to a QoS parametercorresponding to the flow identifier of the first QoS flow, send theflow identifier of the first QoS flow and the flow matching informationto a UPF network element, and send the flow identifier of the first QoSflow and the flow matching information to user equipment.

According to a fourth aspect, a policy control function network elementis provided, including a determining module configured to determine QoSparameters, where the QoS parameters include standardized QoS parameterindication information and a non-standardized QoS parameter, and thenon-standardized QoS parameter includes at least one attribute comprisedin a standardized QoS parameter corresponding to the standardized QoSparameter indication information and a corresponding value of the atleast one attribute, and a sending module configured to send a PCC ruleto a session management function network element, where the PCC ruleincludes the QoS parameters.

With reference to the fourth aspect, in some implementations of thefourth aspect, the standardized QoS parameter indication information isa 5QI parameter value, and the non-standardized QoS parameter includesat least one of the following parameters and a corresponding value: adata PDB, a data PER, an AW, a PL, and an MDBV.

With reference to the fourth aspect, in some implementations of thefourth aspect, the determining module is further configured to receivethe non-standardized QoS parameter from an application function networkelement, or receive first indication information from an applicationfunction network element, and determine the non-standardized QoSparameter according to the first indication information and a firstpre-configured policy, or receive second indication information from thesession management function network element, and determine thenon-standardized QoS parameter according to the second indicationinformation and a second pre-configured policy.

According to a fifth aspect, a communications system is provided, andthe communications system includes the session management functionnetwork element according to any one of the third aspect or the optionalimplementations of the third aspect and the policy control functionnetwork element according to any one of the fourth aspect or theoptional implementations of the fourth aspect.

With reference to the fifth aspect, in some implementations of the fifthaspect, the system further includes an application function networkelement, and the application function network element sends anon-standardized QoS parameter or first indication information to thepolicy control function network element such that the policy controlfunction network element determines the non-standardized QoS parameter,where the non-standardized QoS parameter includes at least one attributecomprised in a standardized QoS parameter corresponding to standardizedQoS parameter indication information and a corresponding value of the atleast one attribute.

According to a sixth aspect, a session management function networkelement is provided, including at least one processor, a memory, and atransceiver. The memory is configured to store an instruction, thetransceiver is used by the session management function network elementto communicate with another device, and the stored instruction isdirectly or indirectly executed by the at least one processor such thatthe session management function network element can perform the methodin any one of the first aspect or the optional implementations of thefirst aspect.

According to a seventh aspect, a policy control function network elementis provided, including at least one processor, a memory, and atransceiver. The memory is configured to store an instruction, thetransceiver is used by the policy control function network element tocommunicate with another device, and the stored instruction is directlyor indirectly executed by the at least one processor such that thepolicy control function network element can perform the method in anyone of the second aspect or the optional implementations of the secondaspect.

According to an eighth aspect, a chip system is provided, including atleast one processor. The at least one processor is configured to executea stored instruction such that a session management function networkelement can perform the method in any one of the first aspect or theoptional implementations of the first aspect.

According to a ninth aspect, a chip system is provided, including atleast one processor. The at least one processor is configured to executea stored instruction such that a policy control function network elementcan perform the method in any one of the second aspect or the optionalimplementations of the second aspect.

According to a tenth aspect, a computer program product is provided. Thecomputer program product includes an instruction, and when theinstruction is executed, a session management function network elementcan perform the method in any one of the first aspect or the optionalimplementations of the first aspect.

According to an eleventh aspect, a computer program product is provided.The computer program product includes an instruction, and when theinstruction is executed, a policy control function network element canperform the method in any one of the second aspect or the optionalimplementations of the second aspect.

According to a twelfth aspect, a computer storage medium is provided.The computer storage medium stores a program instruction, and when theinstruction is executed, a session management function network elementcan perform the method in any one of the first aspect or the optionalimplementations of the first aspect.

According to a thirteenth aspect, a computer storage medium is provided.The computer storage medium stores a program instruction, and when theinstruction is executed, a policy control function network element canperform the method in any one of the second aspect or the optionalimplementations of the second aspect.

BRIEF DESCRIPTION OF DRAWINGS

FIG. 1 is a schematic diagram of an architecture of a network elementcommunications system according to this application;

FIG. 2 is a schematic flowchart of a wireless communication methodaccording to this application;

FIG. 3 is a schematic block diagram of a session management functionnetwork element according to this application;

FIG. 4 is a schematic block diagram of a policy control function networkelement according to this application;

FIG. 5 is a schematic block diagram of a communications apparatusaccording to this application; and

FIG. 6 is a schematic block diagram of a communications system accordingto this application.

DESCRIPTION OF EMBODIMENTS

The following describes technical solutions of this application withreference to the accompanying drawings.

The technical solutions of the embodiments of this application may beapplied to various communications systems, such as a Global System forMobile Communications (GSM), a code-division multiple access (CDMA)system, a wideband CDMA (WCDMA) system, a General Packet Radio Service(GPRS) system, a Long-Term Evolution (LTE) system, an LTEfrequency-division duplex (FDD) system, an LTE time-division duplex(TDD) system, a Universal Mobile Telecommunications System (UMTS), aWorldwide Interoperability for Microwave Access (WIMAX) communicationssystem, a future 5G system, or a New Radio (NR) system.

FIG. 1 is a schematic diagram of a method for determining a network QoSflow and an architecture of a network element communications system 100according to this application. As shown in FIG. 1, the system 100includes a terminal device 110, an access network device 120, a UPFnetwork element 130, a data network (DN) 140, an access and mobilitymanagement function (AMF) network element 150, a session managementfunction (SMF) network element 160, a policy control function (PCF)network element 170, an application function (AF) network element 180,and a unified data management (UDM) network element 190. A connectionmay be established between network elements through a next generation(NG) network interface to implement communication. For example, theterminal device 110 establishes an air interface connection to theaccess network device 120 through a NR interface, to transmit user planedata and control plane signaling. The terminal device 110 may establisha control plane signaling connection to the AMF 150 through an NGinterface 1 (N1). The access network device 120 may establish a userplane data connection to the UPF 130 through an NG interface 3 (N3). Theaccess network device 120 may establish a control plane signalingconnection to the AMF 150 through an NG interface 2 (N2). The UPF 130may establish a control plane signaling connection to the SMF 160through an NG interface 4 (N4). The UPF 130 may exchange user plane datawith the DN through an NG interface 6 (N6). The AMF 150 may establish acontrol plane signaling connection to the SMF 160 through an NGinterface 11 (N11). The SMF 160 may establish a control plane signalingconnection to the PCF 170 through an NG interface 7 (N7). The PCF 170may establish a control plane signaling connection to the AF 180 throughan NG interface 5 (N5). The PCF 170 may establish a control planesignaling connection to the AMF 150 through an NG interface 15 (N15).The UDM 190 may establish a control plane signaling connection to theAMF 150 through an NG interface 8 (N8). The UDM 190 may establish acontrol plane signaling connection to the SMF 160 through an NGinterface 10 (N10).

It should be understood that a name of an interface between networkelements in this application is merely an example, and the interfacebetween the network elements may have another name. The name of theinterface is not limited in this application.

In FIG. 1, the terminal device 110 may be configured to connect, througha wireless air interface, to the access network device 120 deployed byan operator, and then be connected to the DN 140 using the UPF 130. Theaccess network device 120 is mainly configured to implement functionssuch as a wireless physical layer function, resource scheduling, radioresource management, radio access control, and mobility management. TheUPF 130 is configured to perform data flow forwarding, QoS control,charge statistics collection, and the like. The DN 140 may correspond toa plurality of different service domains, such as an Internet Protocol(IP) Multimedia Subsystem (IMS), the Internet, IP television (IPTV), andanother operator service domain, and is mainly configured to provide theterminal device 110 with a plurality of types of data services. The DN140 may include a network device such as a server, a router, or agateway. The AMF 150 is configured to perform access and mobilitymanagement on the terminal device, receive UE mobility and networkselection policies provided by the PCF 170, and execute the policies.The SMF 160 is configured to receive session and service flow controlpolicies provided by the PCF 170, and execute the policies. The PCF 170may generate a PCC rule based on request information of the AF 180, anoperator policy, user subscription information, and the like to controlnetwork behavior, and deliver the PCC rules to a control plane networkelement. The AF 180 mainly provides requirements of an application sidefor a network side, where the requirements include a QoS requirement ofa service flow, a mobility requirement of user equipment, and the like.

The foregoing terminal device 110 may be user equipment, an accessterminal, a subscriber unit, a subscriber station, a mobile station, amobile console, a remote station, a remote terminal, a mobile device, auser terminal, a terminal, a wireless communications device, a useragent, or a user apparatus. The terminal device 110 may alternatively bea cellular phone, a cordless telephone set, a Session InitiationProtocol (SIP) phone, a wireless local loop (WLL) station, a personaldigital assistant (PDA), a handheld device having a wirelesscommunication function, a computing device or another processing deviceconnected to a wireless modem, an in-vehicle device, a wearable device,a terminal device in a future 5G network, a terminal device in a futureevolved Public Land Mobile Network (PLMN), or the like. This is notlimited in the embodiments of this application. The foregoing accessnetwork device may be a device configured to communicate with theterminal device. The access network device may be a base transceiverstation (BTS) in a GSM or CDMA, or may be a NodeB (NB) in a WCDMAsystem, or may be an evolved NodeB (eNB or eNodeB) in an LTE system, ormay be a radio controller in a cloud radio access network (CRAN)scenario. Alternatively, the access network device 120 may be a relaystation, an access point, an in-vehicle device, a wearable device, or anaccess network (AN) device/a radio access network (RAN) device. Anetwork includes a plurality of 5G-AN/5G-RAN nodes. The 5G-AN/5G-RANnode may be an access point (AP), a NG NB (gNB), a gNB whose centralunit (CU) is separated from a distributed unit (DU), a transmissionreception point (TRP), a transmission point (TP), or another accessnode. This is not limited in the embodiments of this application.

Some of the foregoing network elements may work independently, or may becombined to implement some control functions. For example, the AMF 150,the SMF 160, and the PCF 170 may be combined to serve as a managementdevice, to implement access control and mobility management functionssuch as access authentication, security encryption, and locationregistration of the terminal device, session management functions suchas user plane transmission path establishment, release, and change, andfunctions such as analysis of data (such as congestion) related to someslices and data related to the terminal device. As a gateway device, theUPF 130 mainly implements functions such as user plane data routing andforwarding, for example, is responsible for filtering a data packet ofthe terminal device, transmitting/forwarding data, controlling a rate,and generating charging information.

The method for determining a network QoS flow provided in thisapplication may be applied to the session management function networkelement and the policy control function network element. The sessionmanagement function network element and the policy control functionnetwork element each include a hardware layer, an operating system layerrunning above the hardware layer, and an application layer running abovethe operating system layer. The hardware layer includes hardware such asa central processing unit (CPU), a memory management unit (MMU), and amemory (also referred to as a main memory). The operating system layermay be any one or more computer operating systems that process a serviceusing a process, for example, a LINUX operating system, a UNIX operatingsystem, an ANDROID operating system, an IOS operating system, or aWINDOWS operating system. The application layer includes applicationssuch as a browser, a contact list, word processing software, and instantmessaging software.

In addition, aspects or features of this application may be implementedas a method, an apparatus, or a product that uses standardizedprogramming and/or engineering technologies. The term “product” used inthis application covers a computer program that can be accessed from anycomputer readable component, carrier, or medium. For example, a computerreadable medium may include but is not limited to a magnetic storagecomponent (for example, a hard disk, a FLOPPY DISK, or a magnetic tape),an optical disc (for example, a compact disc (CD), a digital versatiledisc (DVID)), a smart card, and a flash memory component (for example,an erasable programmable read-only memory (EPROM), a card, a stick, or akey drive). In addition, various storage media described in thisspecification may indicate one or more devices and/or othermachine-readable media that are configured to store information. Theterm “machine-readable media” may include but is not limited to variousmedia that can store, include, and/or carry an instruction and/or data.

FIG. 1 is merely a diagram of an example architecture. In addition tothe functional units shown in FIG. 1, the network architecture mayfurther include another functional unit or functional entity. This isnot limited in the embodiments of the present disclosure.

To better understand this application, the following describes thisapplication with reference to FIG. 2 to FIG. 5 using, as an example, asystem that is the same as or similar to the system shown in FIG. 1.

FIG. 2 is a schematic flowchart of a wireless communication method 200according to this application. As shown in FIG. 2, the method 200includes the following steps.

Step 210: A policy control function network element determines QoSparameters.

The QoS parameters include standardized QoS parameter indicationinformation and a non-standardized QoS parameter, and thenon-standardized QoS parameter includes at least one attribute comprisedin a standardized QoS parameter corresponding to the standardized QoSparameter indication information and a corresponding value of the atleast one attribute.

The QoS parameters indicate network QoS parameters of a QoS flow thatmatches a PCC rule. The QoS parameters may be divided into astandardized QoS parameter and a non-standardized QoS parameter. Thestandardized QoS parameters are a set of QoS parameters that can bedetermined using the standardized QoS parameter indication information.The non-standardized QoS parameter is a QoS parameter dynamically fromthe policy control function network element, and the non-standardizedQoS parameter includes the at least one attribute comprised in thestandardized QoS parameter corresponding to the standardized QoSparameter indication information and a corresponding value of the atleast one attribute.

Step 220: The policy control function network element sends a PCC ruleto a session management function network element, where the PCC ruleincludes the QoS parameters.

Step 230: The session management function network element receives thePCC rule from the policy control function network element.

Step 240: The session management function network element determines,based on the standardized QoS parameter indication information and thenon-standardized QoS parameter, a QoS flow corresponding to the PCCrule.

Therefore, in this embodiment of this application, the policy controlfunction network element determines the QoS parameters, and sends thePCC rule including the QoS parameters to the session management functionnetwork element, and the session management function network elementdetermines, using both the standardized QoS parameter indicationinformation and the non-standardized QoS parameter, the QoS flowcorresponding to the PCC rule, thereby increasing an accuracy rate ofdetermining the QoS flow corresponding to the PCC rule, and accordinglyguaranteeing network QoS of a data service transmitted using the QoSflow.

It should be understood that, before step 210, the session managementfunction network element obtains address information or domain nameinformation of the policy control function network element, and mayfind, through addressing, the policy control function network elementbased on the address information or the domain name information, or thepolicy control function network element receives a request message fromthe session management function network element, where the requestmessage includes address information or domain name information of thesession management function network element, and may find, throughaddressing, the session management function network element based on theaddress information or the domain name information. The sessionmanagement function network element may initiate a PCC rule request, andthe policy control function network element may initiate a PCC ruleupdate.

Optionally, the standardized QoS parameter indication information is a5QI parameter value, and the non-standardized QoS parameter includes atleast one of the following parameters: a data PDB, a data PER, an AW, aPL, and an MDBV.

Further, the 5QI parameter value is an index value, and one standardizedQoS parameter can be determined based on the index value. Thestandardized QoS parameter includes a set of attributes andcorresponding values, as shown in Table 1.

TABLE 1 Standardized 5QI parameter 5Q1 param- Re- Averaging Service etersource Data Data time exam- value type PL PDB PER MDBV window ple 1 GBR20 100 10⁻² N/A TBD Voice milli- service seconds(ms)

In Table 1, that the 5QI parameter value is 1 indicates a set of 5QIparameters in which the Resource Type is a guaranteed bit rate (GBR)type, the PL is 20, the PDB parameter is 100 ms, the PER is 10², and theMDBV and the AW are to be defined. That the 5QI parameter value is 1indicates a set of parameters specified in a network protocol.

It should be understood that Table 1 merely shows a standardized QoSparameter corresponding to one 5QI parameter value. In practice, theremay be different standardized QoS parameters corresponding to different5QI parameter values.

Optionally, that a policy control function network element determinesQoS parameters in step 210 includes the policy control function networkelement receives the non-standardized QoS parameter from an applicationfunction network element, or the policy control function network elementreceives first indication information from an application functionnetwork element, and the policy control function network elementdetermines the non-standardized QoS parameter according to the firstindication information and a first pre-configured policy, or the policycontrol function network element receives second indication informationfrom the session management function network element, and the policycontrol function network element determines the non-standardized QoSparameter according to the second indication information and a secondpre-configured policy.

Further, the policy control function network element receives thenon-standardized QoS parameter from the application function networkelement. To be specific, the policy control function network elementdirectly adds, to the PCC rule, the non-standardized QoS parameter fromthe application function network element, and sends the PCC rule to thesession management function network element.

The first indication information may be application identifierinformation or 5-tuple information (including a source IP address, asource port, a destination IP address, a destination port, and atransport layer protocol) from the application function network element.The first indication information is indication information for thepolicy control function network element determining the non-standardizedQoS parameter, and the policy control function network elementdetermines the non-standardized QoS parameter according to the firstindication information and the first pre-configured policy. The firstpre-configured policy includes operator configuration information, usersubscription information, and/or the like. The operator configurationinformation may be the following information a QoS parameterconfiguration for a specific application, or a pre-configurationoperation, for example, parameter information, such as a bandwidthguarantee and a scheduling priority, pre-configured by an operator for aspecific application, or gating information set for a specificapplication. The user subscription information may be the followinginformation a user level, a specific-application value-added service towhich a user subscribes, a user subscription package, and the like.

The second indication information may be request information from thesession management function network element, and is used to request thePCF 170 to adjust the QoS parameters in the PCC rule. The secondindication information may include an application event detectionreport, resource-constrained notification information, and/or the like.The application event detection report may carry an applicationidentifier, and the resource-constrained notification information maycarry a PCC rule ID.

In this case, the policy control function network element determines thenon-standardized QoS parameter such that the policy control functionnetwork element can dynamically determine the QoS parameters in realtime to adjust the PCC rule in a timely manner, and then determine a QoSflow corresponding to an adjusted PCC rule, thereby increasing anaccuracy rate of determining the QoS flow corresponding to the PCC rule,and accordingly improving network QoS of a data service.

Optionally, determining a QoS flow corresponding to the PCC rule in step240 includes when there is a first QoS flow that matches both thestandardized QoS parameter indication information and thenon-standardized QoS parameter, determining, by the session managementfunction network element, the first QoS flow as the QoS flowcorresponding to the PCC rule, or when there is no QoS flow that matchesboth the standardized QoS parameter indication information and thenon-standardized QoS parameter, determining, by the session managementfunction network element, a second QoS flow as the QoS flowcorresponding to the PCC rule, where QoS parameters corresponding to thesecond QoS flow are determined according to the PCC rule.

A 5G network is used as an example. It is assumed that a first QoS flowexists on the session management function network element, QoSparameters corresponding to the first QoS flow are (5QI: 1, PL: 301, andthe QoS parameters included in the PCC rule from the policy controlfunction network element are {5QI: 1, PL: 30}. Because the first QoSflow whose QoS parameters match (5QI: 1, PL: 30) exists on the sessionmanagement function network element, the session management functionnetwork element binds the first QoS flow to the PCC rule.

It is assumed that a first QoS flow exists on the session managementfunction network element, QoS parameters corresponding to the first QoSflow are {5QI: 1, PL: 10}, and the QoS parameters included in the PCCrule from the policy control function network element are {5QI: 1, PL:30}. Because no QoS flow whose QoS parameters match (5QI: 1, PL: 30)exists on the session management function network element, the sessionmanagement function network element creates a new second QoS flow forthe PCC rule. QoS parameters corresponding to the second QoS flow aredetermined according to the PCC rule. To be specific, the QoS parameterscorresponding to the second QoS flow are {5QI: 1, PL: 30}.

Optionally, in step 240, the PCC rule further includes a firstparameter, and the first parameter is any parameter that can representQoS and that is other than the standardized QoS parameter and thenon-standardized QoS parameter.

Determining a QoS flow corresponding to the PCC rule includes when thereis a first QoS flow that matches all of the standardized QoS parameterindication information, the non-standardized QoS parameter, and thefirst parameter, determining, by the session management function networkelement, the first QoS flow as the QoS flow corresponding to the PCCrule, or when there is no QoS flow that matches all of the standardizedQoS parameter indication information, the non-standardized QoSparameter, and the first parameter, determining, by the sessionmanagement function network element, a second QoS flow as the QoS flowcorresponding to the PCC rule, where QoS parameters corresponding to thesecond QoS flow are determined according to the PCC rule.

Further, the first parameter may include an ARP and/or a QNC parameter.

A 5G network is used as an example. It is assumed that a first QoS flowexists on the session management function network element, QoSparameters corresponding to the first QoS flow are {5QI: 1, ARP: 2, PL:30}, and the QoS parameters included in the PCC rule from the policycontrol function network element are {5QI: 1, ARP: 2, PL: 30}. Becausethe first QoS flow whose QoS parameters match {5QI: 1, ARP: 2, PL: 30}exists on the session management function network element, the sessionmanagement function network element binds the first QoS flow to the PCCrule.

It is assumed that a first QoS flow exists on the session managementfunction network element, QoS parameters corresponding to the first QoSflow are {5QI: 1, ARP: 3, PL: 10}, and the QoS parameters included inthe PCC rule from the policy control function network element are {5QI:1, ARP: 2, PL: 30}. Because no QoS flow whose QoS parameters match {5QI:1, ARP: 2, PL: 30} exists on the session management function networkelement, the session management function network element creates a newsecond QoS flow for the PCC rule. QoS parameters corresponding to thesecond QoS flow are determined according to the PCC rule. To bespecific, the QoS parameters corresponding to the second QoS flow are(5QI: 1, ARP: 2, PL: 30).

In this case, when the PCC rule further includes the first parameter,the QoS flow corresponding to the PCC rule is determined using thestandardized QoS parameter indication information, the non-standardizedQoS parameter, and the first parameter such that an accuracy rate ofdetermining the QoS flow corresponding to the PCC rule can be furtherincreased.

Optionally, the PCC rule may further include the following parametersuplink (UL) and downlink (DL) maximum service flow bandwidths (UL and DLMaximum Flow BitRate), uplink and downlink guaranteed service flowbandwidths (UL and DL Guaranteed Flow BitRate), and a precedence. Theprecedence indicates a precedence of the PCC rule, to be specific,precedence processing performed when a data flow can match a pluralityof PCC rules.

Optionally, the PCC rule further includes flow matching information.When the session management function network element determines thesecond QoS flow as the QoS flow corresponding to the PCC rule, themethod 200 further includes sending, by the session management functionnetwork element, a flow identifier of the second QoS flow and the QoSparameters to an access network, sending, by the session managementfunction network element, the flow identifier of the second QoS flow andthe flow matching information to a UPF network element, and sending, bythe session management function network element, the flow identifier ofthe second QoS flow and the flow matching information to user equipment.

Further, the session management function network element sends the QoSflow identifier (QFI) 2 of the second QoS flow and the QoS parameters tothe access network such that the access network executes, when receivinga data packet whose header includes a QFI 2 marking, a QoS guaranteepolicy corresponding to the QFI 2 for the data packet.

It should be understood that the QoS parameter from the sessionmanagement function network element to the access network may also bereferred to as a QoS profile.

The session management function network element sends the QFI 2 and theflow matching information to the UPF network element. The flow matchinginformation is included in the PCC rule from the policy control functionnetwork element, and the flow matching information is used to instructto add the QFI 2 marking to a header of a data packet of a service dataflow that matches the flow matching information. The flow matchinginformation indicates a specific service data flow for which the PCCrule should be executed. The flow matching information is packet filterset information, and includes IP quintuplets (including a source IPaddress, a source port, a destination IP address, a destination port,and a transport layer protocol). When the UPF 130 receives a downlinkdata packet, the UPF 130 matches the downlink data packet with thecorresponding second QoS flow based on a destination address of thedownlink data packet and the flow matching information, and adds the QFI2 marking to a header of the data packet. When receiving the data packetincluding the QFI 2 marking, the access network provides the data packetwith a service guarantee of the QoS flow corresponding to the QFI 2.

The session management function network element sends the flowidentifier of the second QoS flow and the flow matching information tothe user equipment. When sending an uplink data packet, the userequipment matches the uplink data packet with the corresponding secondQoS flow based on a destination address of the uplink data packet andthe flow matching information, and adds the QFI 2 marking to a header ofthe data packet. When receiving the data packet including the QFI 2marking, the access network provides the data packet with a serviceguarantee of the QoS flow corresponding to the QFI 2.

It should be understood that, the foregoing describes a case in whichwhen the flow matching information included in the PCC rule is thepacket filter set information, the session management function networkelement delivers the flow identifier and the flow matching informationto both the user equipment and the UPF network element. However, whenthe flow matching information included in the PCC rule is an applicationidentifier, the application identifier may not be sent to the userequipment, and therefore the UE may have no uplink flow matchinginformation. The user equipment transmits an uplink data packet based ona default QoS flow. For example, the default QoS flow may be a QoS flowof a lowest matching priority. The session management function networkelement sends the application identifier and the flow identifier to theUPF network element. When receiving a downlink data packet, the UPFnetwork element performs matching according to the applicationidentifier and an application matching rule, and adds the flowidentifier to a header of the downlink data packet if the matchingsucceeds. When the flow matching information included in the PCC rule isan application identifier, the session management function networkelement may alternatively send the application identifier and the flowidentifier to the user equipment. The user equipment may determine anapplication type using information such as a peer uniform resourcelocator (URL) or a domain name address. If the determined applicationtype is consistent with the application identifier, the user equipmentadds the flow identifier to a header of the uplink data packet.

Optionally, the PCC rule further includes flow matching information.When the session management function network element determines thefirst QoS flow as the QoS flow corresponding to the PCC rule, the method200 further includes sending, by the session management function networkelement, a flow identifier of the first QoS flow and a second parameterto an access network, where the second parameter is indicationinformation for the access network updating a value of an attributecorresponding to a QoS parameter corresponding to the flow identifier ofthe first QoS flow, sending, by the session management function networkelement, the flow identifier of the first QoS flow and the flow matchinginformation to a UPF network element, and sending, by the sessionmanagement function network element, the flow identifier of the firstQoS flow and the flow matching information to user equipment.

Further, the session management function network element sends the flowidentifier QFI 1 of the first QoS flow and the second parameter to theaccess network. The second parameter is indication information for theaccess network updating the value of the attribute corresponding to theQoS parameter corresponding to the flow identifier of the first QoSflow. For example, the second parameter is (GBR: 5 megabytes (MB)), andoriginal QoS parameters corresponding to the first QoS flow are {5QI: 1,GBR: 3 MB, ARP: 2, PL: 20}. After receiving the flow identifier QFI 1 ofthe first QoS flow and the second parameter, the access network changesthe QoS parameters corresponding to the first QoS flow to {5QI: 1, GBR:5 MB, ARP: 2, PL: 20}. When receiving a data packet whose headerincludes a QFI 1 marking, the access network executes, for the datapacket, a changed QoS guarantee policy corresponding to the QFI 1.

It should be understood that, for a specific process in which thesession management function network element sends the flow identifier ofthe first QoS flow and the flow matching information to each of the UPFnetwork element and the user equipment, correspondingly refer to aprocess in which the session management function network element sendsthe flow identifier of the second QoS flow and the flow matchinginformation to each of the UPF network element and the user equipment.To avoid repetition, details are not described herein again.

FIG. 3 is a schematic block diagram of a session management functionnetwork element 300 according to this application. As shown in FIG. 3,the session management function network element 300 includes thefollowing modules a receiving module 310 configured to receive a PCCrule from a policy control function network element, where the PCC ruleincludes QoS parameters, the QoS parameters include standardized QoSparameter indication information and a non-standardized QoS parameter,and the non-standardized QoS parameter includes at least one attributecomprised in a standardized QoS parameter corresponding to thestandardized QoS parameter indication information and a correspondingvalue of the at least one attribute, and a determining module 320configured to determine, based on the standardized QoS parameterindication information and the non-standardized QoS parameter, a QoSflow corresponding to the PCC rule.

Optionally, the receiving module 310 and the determining module 320 areconfigured to perform operations of the method 200 for determining anetwork QoS flow in this application. For brevity, details are notdescribed herein again.

FIG. 4 is a schematic block diagram of a policy control function networkelement 400 according to this application. As shown in FIG. 4, thepolicy control function network element includes the following modules adetermining module 410 configured to determine QoS parameters, where theQoS parameters include standardized QoS parameter indication informationand a non-standardized QoS parameter, and the non-standardized QoSparameter includes at least one attribute comprised in a standardizedQoS parameter corresponding to the standardized QoS parameter indicationinformation and a corresponding value of the at least one attribute, anda sending module 420 configured to send a PCC rule to a sessionmanagement function network element, where the PCC rule includes the QoSparameters.

Optionally, the determining module 410 and the sending module 420 areconfigured to perform operations of the method 200 for determining anetwork QoS flow in this application. For brevity, details are notdescribed herein again.

The session management function network element and the policy controlfunction network element completely correspond to the session managementfunction network element and the policy control function network elementin the method embodiment, and a corresponding module performs acorresponding step. For details, refer to the corresponding methodembodiment.

FIG. 5 is a schematic block diagram of a communications apparatus 500according to this application. The communications apparatus 500 includesa memory 510 configured to store a program, where the program includescode, a transceiver 520 configured to communicate with another device,and a processor 530 configured to execute the program code in the memory510.

Optionally, when the code is executed, the processor 530 may implementoperations of the method 200. For brevity, details are not describedherein again. The transceiver 520 is configured to perform specificsignal receiving/sending under the driving of the processor 530.

The communications apparatus 500 may be the session management functionnetwork element or the policy control function network element. Theprocessor performs an operation of the determining module. Thetransceiver may include a transmitter and/or a receiver, whichrespectively perform corresponding steps of the sending module and thereceiving module.

FIG. 6 is a schematic block diagram of a communications system 600according to this application. The communications system 600 includes asession management function network element 610 and a policy controlfunction network element 620. For a connection between the sessionmanagement function network element 610 and the policy control functionnetwork element 620, refer to corresponding descriptions in the systemarchitecture in FIG. 1.

Optionally, the communications system 600 further includes anapplication function network element. The application function networkelement sends a non-standardized QoS parameter or first indicationinformation to the policy control function network element to instructthe policy control function network element to determine thenon-standardized QoS parameter. The non-standardized QoS parameterincludes at least one attribute comprised in a standardized QoSparameter corresponding to standardized QoS parameter indicationinformation and a corresponding value of the at least one attribute.

Further, the policy control function network element receives thenon-standardized QoS parameter from the application function networkelement. To be specific, the policy control function network elementdirectly adds, to a PCC rule, the non-standardized QoS parameter fromthe application function network element, and sends the PCC rule to thesession management function network element.

The first indication information may be application identifierinformation or 5-tuple information (including a source IP address, asource port, a destination IP address, a destination port, and atransport layer protocol) from the application function network element.The first indication information is indication information for thepolicy control function network element determining the non-standardizedQoS parameter.

It should be understood that the session management function networkelement 610 and the policy control function network element 620 areconfigured to perform operations of the method 200 for determining anetwork QoS flow in this application. For brevity, details are notdescribed herein again.

The session management function network element and the policy controlfunction network element completely correspond to the session managementfunction network element and the policy control function network elementin the method embodiment. For details, refer to the corresponding methodembodiment.

It should be understood that the communications system 600 may furtherinclude another network element or functional entity. This is notlimited in this embodiment of the present disclosure.

A person of ordinary skill in the art may be aware that, in combinationwith the examples described in the embodiments disclosed in thisspecification, units and algorithm steps can be implemented byelectronic hardware or a combination of computer software and electronichardware. Whether the functions are performed by hardware or softwaredepends on particular applications and design constraints of thetechnical solutions. A person skilled in the art may use differentmethods to implement the described functions for each particularapplication, but it should not be considered that the implementationgoes beyond the scope of this application.

It may be clearly understood by a person skilled in the art that, forthe purpose of convenient and brief description, for a detailed workingprocess of the foregoing system, apparatus, and unit, refer to acorresponding process in the foregoing method embodiment. Details arenot described herein again.

In the several embodiments provided in this application, it should beunderstood that the disclosed system, apparatus, and method may beimplemented in other manners. For example, the described apparatusembodiment is merely an example. For example, the unit division ismerely logical function division and may be other division during actualimplementation. For example, a plurality of units or components may becombined or integrated into another system, or some features may beignored or not performed. In addition, the displayed or discussed mutualcouplings or direct couplings or communication connections may beimplemented through some interfaces. The indirect couplings orcommunication connections between the apparatuses or units may beimplemented in electrical, mechanical, or other forms.

The units described as separate parts may or may not be physicallyseparate, and parts displayed as units may or may not be physical units,may be located in one position, or may be distributed on a plurality ofnetwork units. Some or all of the units may be selected based on actualrequirements to achieve the objectives of the solutions of theembodiments.

In addition, functional units in the embodiments of this application maybe integrated into one processing unit, or each of the units may existalone physically, or two or more units are integrated into one unit.

It should be understood that the terms “and/or” and “at least one of Aor B” in this specification describe only an association relationshipfor describing associated objects and represent that three relationshipsmay exist. For example, A and/or B may represent the following threecases Only A exists, both A and B exist, and only B exists. In addition,the character “/” in this specification generally indicates an “or”relationship between the associated objects.

An embodiment of this application provides a computer readable mediumconfigured to store a computer program. The computer program includes aninstruction for performing the method for determining a network QoS flowin the foregoing embodiment of this application in FIG. 2. When thefunctions are implemented in a form of a software functional unit andsold or used as an independent product, the functions may be stored in acomputer readable storage medium. Based on such an understanding, thetechnical solutions of this application essentially, or the partcontributing to the other approaches, or some of the technical solutionsmay be implemented in a form of a software product. The computersoftware product is stored in a storage medium, and includes severalinstructions for instructing a computer device (which may be a personalcomputer, a server, a network device, or the like) to perform all orsome of the steps of the methods described in the embodiments of thisapplication. The foregoing storage medium includes any medium that canstore program code, such as a Universal Serial Bus (USB) flash drive, aremovable hard disk, a read-only memory (ROM), a random-access memory(RAM), a magnetic disk, or an optical disc.

All or some of the foregoing embodiments may be implemented throughsoftware, hardware, firmware, or any combination thereof. When softwareis used to implement the embodiments, the embodiments may be implementedfully or partially in a form of a computer program product. The computerprogram product includes one or more computer instructions. When thecomputer program instructions are loaded and executed on a computer, theprocedures or functions according to this application are fully orpartially generated. The computer may be a general-purpose computer, aspecial-purpose computer, a computer network, or other programmableapparatuses. The computer instructions may be stored in a computerreadable storage medium or may be transmitted from a computer readablestorage medium to another computer readable storage medium. For example,the computer instructions may be transmitted from a website, computer,server, or data center to another website, computer, server, or datacenter in a wired (for example, a coaxial cable, an optical fiber, or adigital subscriber line) or wireless (for example, infrared, radio, ormicrowave) manner. The computer readable storage medium may be anyusable medium accessible by the computer, or a data storage device, suchas a server or a data center, integrating one or more usable media. Theusable medium may be a magnetic medium (for example, a floppy disk, ahard disk, or a magnetic tape), an optical medium, or a semiconductormedium (for example, a solid state disk (Solid State Disk (SSD))), orthe like.

The foregoing descriptions are merely specific implementations of thisapplication, but are not intended to limit the protection scope of thisapplication. Any variation or replacement readily figured out by aperson skilled in the art within the technical scope disclosed in thisapplication shall fall within the protection scope of this application.Therefore, the protection scope of this application shall be subject tothe protection scope of the claims.

1. A method for determining a network quality of service (QoS) flow,wherein the method comprises: receiving, by a session managementfunction network element, a policy and charging control (PCC) rule froma policy control function network element, wherein the PCC rulecomprises a standardized 5^(th) generation (5G) QoS identifier (5QI)parameter value and a non-standardized QoS parameter, and wherein thenon-standardized QoS parameter comprises at least one attribute in astandardized QoS parameter corresponding to the standardized 5QIparameter value and a corresponding value of the at least one attribute;determining, by the session management function network element based onthe standardized 5QI parameter value and the non-standardized QoSparameter, a QoS flow corresponding to the PCC rule; and binding, by thesession management function network element, the PCC rule to the QoSflow.
 2. The method of claim 1, wherein the standardized QoS parametercomprises a set of specified attributes and corresponding specifiedvalues, and wherein the set of specified attributes comprises at leastone of a data packet delay budget (PDB), a data packet error rate (PER),an averaging window (AW), a priority level (PL), or a maximum data burstvolume (MDBV).
 3. The method of claim 2, wherein a value correspondingto an attribute in the non-standard QoS parameter is different from avalue of a same attribute corresponding to the standardized 5QIparameter value.
 4. The method of claim 1, further comprising:determining, by the policy control function network element, the PCCrule; and sending, by the policy control function network element, thePCC rule to the session management function network element.
 5. Themethod of claim 1, wherein determining the QoS flow further comprises:determining, by the session management function network element, whethera first QoS flow exists whose first QoS parameters match both thestandardized 5QI parameter value and the non-standardized QoS parameter;and determining, by the session management function network element, thefirst QoS flow as the QoS flow corresponding to the PCC rule when thefirst QoS flow exists.
 6. The method of claim 5, wherein the PCC rulefurther comprises flow matching information, and wherein the methodfurther comprises: sending, by the session management function networkelement, a flow identifier of the first QoS flow and a second parameterto an access network, wherein the second parameter comprises indicationinformation for the access network to update a value of an attributecorresponding to the first QoS parameters of the first QoS flow; andsending, by the session management function network element, the flowidentifier and the flow matching information to a user plane function(UPF) network element.
 7. The method of claim 1, wherein determining theQoS flow further comprises: determining, by the session managementfunction network element, whether a first QoS flow exists whose firstQoS parameters match both the standardized 5QI parameter value and thenon-standardized QoS parameter; and determining, by the sessionmanagement function network element, a new QoS flow as the QoS flowcorresponding to the PCC rule when the first QoS flow does not exist,wherein new QoS parameters corresponding to the new QoS flow are basedon the PCC rule.
 8. The method of claim 7, wherein the PCC rule furthercomprises flow matching information, and wherein the method furthercomprises: sending, by the session management function network element,a flow identifier of the new QoS flow, the standardized 5QI parametervalue, and the non-standardized QoS parameter to an access network; andsending, by the session management function network element, the flowidentifier and the flow matching information to a user plane function(UPF) network element.
 9. The method of claim 1, wherein the PCC rulefurther comprises a first parameter, wherein the first parameterrepresents a QoS parameter other than the standardized 5QI parametervalue and the non-standardized QoS parameter, and wherein determiningthe QoS flow further comprises: determining, by the session managementfunction network element, whether a first QoS flow exists whose firstQoS parameters match the standardized 5QI parameter value, thenon-standardized QoS parameter, and the first parameter; anddetermining, by the session management function network element, thefirst QoS flow as the first QoS flow corresponding to the PCC rule whenthe first QoS flow exists.
 10. The method of claim 9, wherein the PCCrule further comprises flow matching information, and wherein the methodfurther comprises: sending, by the session management function networkelement, a flow identifier of the first QoS flow and a second parameterto an access network, wherein the second parameter comprises indicationinformation for the access network to update a value of an attributecorresponding to the QoS parameters of the QoS flow; and sending, by thesession management function network element, the flow identifier and theflow matching information to a user plane function (UPF) networkelement.
 11. The method of claim 9, wherein the first parametercomprises at least one of a QoS notification control (QNC) parameter oran allocation and retention priority (ARP) parameter.
 12. The method ofclaim 1, wherein the PCC rule further comprises a first parameter,wherein the first parameter represents a QoS parameter other than thestandardized 5QI parameter value and the non-standardized QoS parameter,wherein determining the QoS flow further comprises: determining, by thesession management function network element, whether a first QoS flowexists whose first QoS parameters match the standardized 5QI parametervalue, the non-standardized QoS parameter, and the first parameter; anddetermining, by the session management function network element, a newQoS flow as the QoS flow corresponding to the PCC rule when the firstQoS flow does not exist, wherein new QoS parameters corresponding to thenew QoS flow are based on the PCC rule.
 13. The method of claim 12,wherein the PCC rule further comprises flow matching information, andwherein the method further comprises: sending, by the session managementfunction network element, a flow identifier of the new QoS flow, thestandardized 5QI parameter value, and the non-standardized QoS parameterto an access network; and sending, by the session management functionnetwork element, the flow identifier and the flow matching informationto a user plane function (UPF) network element.
 14. A session managementfunction network element comprising: a memory configured to storeprogram instructions; and a processor coupled to the memory andconfigured to execute the program instructions to cause the sessionmanagement function network element to: receive a policy and chargingcontrol (PCC) rule from a policy control function network element,wherein the PCC rule comprises a standardized 5^(th) generation (5G)quality of service (QoS) identifier (5QI) parameter value and anon-standardized QoS parameter, and wherein the non-standardized QoSparameter comprises at least one attribute in a standardized QoSparameter corresponding to the standardized 5QI parameter value and acorresponding value of the at least one attribute; determine, based onthe standardized 5QI parameter value and the non-standardized QoSparameter, a QoS flow corresponding to the PCC rule; and bind the PCCrule to the QoS flow.
 15. The session management function networkelement of claim 14, wherein the standardized QoS parameter comprises aset of specified attributes and corresponding specified values, andwherein the set of specified attributes comprises at least one of a datapacket delay budget (PDB), a data packet error rate (PER), an averagingwindow (AW), a priority level (PL), or a maximum data burst volume(MDBV).
 16. The session management function network element of claim 15,wherein a value corresponding to an attribute in the non-standard QoSparameter is different from a value of a same attribute corresponding tothe standardized 5QI parameter value.
 17. The session managementfunction network element of claim 14, wherein the program instructions,when executed by the processor, further cause the session managementfunction network element to: determine whether a first QoS flow existswhose first QoS parameters match both the standardized 5QI parametervalue and the non-standardized QoS parameter; and determine the firstQoS flow as the QoS flow corresponding to the PCC rule when the firstQoS flow exists.
 18. The session management function network element ofclaim 17, wherein the PCC rule further comprises flow matchinginformation, and wherein the program instructions, when executed by theprocessor, further cause the session management function network elementto: send a flow identifier of the first QoS flow and a second parameterto an access network, wherein the second parameter comprises indicationinformation for the access network to update a value of an attributecorresponding to the QoS parameters of the first QoS flow; and send theflow identifier and the flow matching information to a user planefunction (UPF) network element.
 19. The session management functionnetwork element of claim 14, wherein the program instructions, whenexecuted by the processor, further cause the session management functionnetwork element to: determine whether a first QoS flow exists whosefirst QoS parameters match both the standardized 5QI parameter value andthe non-standardized QoS parameter; and determine a new QoS flow as theQoS flow corresponding to the PCC rule when the first QoS flow does notexist, wherein new QoS parameters corresponding to the new QoS flow arebased on the PCC rule.
 20. The session management function networkelement of claim 19, wherein the PCC rule further comprises flowmatching information, and wherein the program instructions, whenexecuted by the processor, further cause the session management functionnetwork element to: send a flow identifier of the new QoS flow, thestandardized 5QI parameter value, and the non-standardized QoS parameterto an access network; and send the flow identifier and the flow matchinginformation to a user plane function (UPF) network element.
 21. Thesession management function network element of claim 14, wherein the PCCrule further comprises a first parameter, wherein the first parameterrepresents a QoS parameter other than the standardized 5QI parametervalue and the non-standardized QoS parameter, and wherein the programinstructions, when executed by the processor, further cause the sessionmanagement function network element to: determine whether a first QoSflow exists whose first QoS parameters match the standardized 5QIparameter value, the non-standardized QoS parameter, and the firstparameter; and determine the first QoS as the QoS flow corresponding tothe PCC rule when the first QoS flow exists.
 22. The session managementfunction network element of claim 21, wherein the PCC rule furthercomprises flow matching information, and wherein the programinstructions, when executed by the processor, further cause the sessionmanagement function network element to: send a flow identifier of thefirst QoS flow and a second parameter to an access network, wherein thesecond parameter comprises indication information for the access networkto update a value of an attribute corresponding to the QoS parameters ofthe first QoS flow; and send the flow identifier and the flow matchinginformation to a user plane function (UPF) network element.
 23. Thesession management function network element of claim 21, wherein thefirst parameter comprises one or more of an allocation and retentionpriority (ARP) parameter or a QoS notification control (QNC) parameter.24. The session management function network element of claim 14, whereinthe PCC rule further comprises a first parameter, wherein the firstparameter represents a QoS parameter other than the standardized 5QIparameter value and the non-standardized QoS parameter, wherein theprogram instructions, when executed by the processor, further cause thesession management function network element to: determine whether afirst QoS flow exists whose first QoS parameters match the standardized5QI parameter value, the non-standardized QoS parameter, and the firstparameter; and determine a new QoS flow as the QoS flow corresponding tothe PCC rule when the first QoS flow does not exist, wherein new QoSparameters corresponding to the new QoS flow are based on the PCC rule.25. The session management function network element of claim 24, whereinthe PCC rule further comprises flow matching information, and whereinthe program instructions, when executed by the processor, further causethe session management function network element to: send a flowidentifier of the new QoS flow, the standardized 5QI parameter value,and the non-standardized QoS parameter to an access network; and sendthe flow identifier and the flow matching information to a user planefunction (UPF) network element.
 26. The session management functionnetwork element of claim 24, wherein the first parameter comprises oneor more of an allocation and retention priority (ARP) parameter or a QoSnotification control (QNC) parameter.